From ce4d8843a4087b1672f8b107c6b0ea06b77d7ef7 Mon Sep 17 00:00:00 2001 From: Gerd Moellmann Date: Mon, 11 Dec 2000 14:50:07 +0000 Subject: [PATCH] (try_cursor_movement): Check update_mode_lines instead of the window's update_mode_line flag, since the former is set by force-mode-line-update, not the latter. This makes column-number-mode slightly faster. --- src/xdisp.c | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/src/xdisp.c b/src/xdisp.c index 444c7696f68..6e0b565b264 100644 --- a/src/xdisp.c +++ b/src/xdisp.c @@ -9144,16 +9144,14 @@ try_cursor_movement (window, startp, scroll_step) not moved off the frame. */ if (/* Point may be in this window. */ PT >= CHARPOS (startp) - /* If we don't check this, we are called to move the cursor in a - horizontally split window with a current matrix that doesn't - fit the display. */ - && !windows_or_buffers_changed /* Selective display hasn't changed. */ && !current_buffer->clip_changed - /* If force-mode-line-update was called, really redisplay; - that's how redisplay is forced after e.g. changing - buffer-invisibility-spec. */ - && NILP (w->update_mode_line) + /* Function force-mode-line-update is used to force a thorough + redisplay. It sets either windows_or_buffers_changed or + update_mode_lines. So don't take a shortcut here for these + cases. */ + && !update_mode_lines + && !windows_or_buffers_changed /* Can't use this case if highlighting a region. When a region exists, cursor movement has to do more than just set the cursor. */ -- 2.30.2